Purpose

The purpose of the CM Plan is to define, or reference, the steps and activities that describe how Configuration and Change Control Management (CM) is to be performed in the development of a software product.

Brief Outline

(hyperlinks into HTML template in a new window)

1.       Introduction         

    1.1     Purpose     

    1.2     Scope     

    1.3     Definitions, Acronyms and Abbreviations     

    1.4     References     

    1.5     Overview     

2.       Software Configuration Management

    2.1     Organization, Responsibilities and Interfaces     

    2.2     Tools, Environment and Infrastructure     

3.       The CM Program         

    3.1     Configuration Identification     

        3.1.1         Identification Methods           

        3.1.2         Project Baselines           

    3.2     Configuration and Change Control     

        3.2.1         Change Request Processing and Approval           

        3.2.2         Change Control Board (CCB)           

    3.3     Configuration Status Accounting     

        3.3.1         Project Media Storage and Release Process           

        3.3.2         Reports and Audits           

4.       Milestones

5.       Training and Resources     

6.       Subcontractor and Vendor Software Control

Timing

The CM Plan is written early in the Elaboration phase once funding has been approved for the project to proceed. It should be re-visited at the start of each phase and updated accordingly. The CM Plan needs to be archived such that it is available for post-deployment maintenance activities for guidance on where certain software assets might be stored.

Responsibility

The Worker: Configuration Manager is responsible for the integrity of the CM Plan, ensuring that it:

• covers the activities to be performed,

• the schedule of activities,

• the assigned responsibilities, and

• the required resources (staff, tools, environment and infrastructure)